Skip to content

Conversation

@khalidhuseynov
Copy link
Member

@khalidhuseynov khalidhuseynov commented Jun 11, 2016

What is this PR for?

This PR is to make available information on the currently authenticated user(subject) in the Notebook storage level. It can be used for multiple purposes (ACL, login to third parties, etc.) once storage layer is user aware. It basically updates NotebookRepo api with additional user info

What type of PR is it?

Improvement

Todos

  • - add authInfo(subject) to list()
  • - add authInfo(subject) to get()
  • - add authInfo(subject) to save()
  • - add authInfo(subject) to remove()

What is the Jira issue?

How should this be tested?

storage layer should be working as before with and without authenticated user, green CI

Screenshots (if appropriate)

Questions:

  • Does the licenses files need update? No
  • Is there breaking changes for older versions? not breaking, but some api changes
  • Does this needs documentation? No

@khalidhuseynov khalidhuseynov changed the title Update api/pass auth info to repo Authenticated user aware notebook storage layer Jun 11, 2016
@khalidhuseynov khalidhuseynov force-pushed the update-api/pass-auth-info-to-repo branch 10 times, most recently from 049c663 to 1cfba76 Compare June 14, 2016 07:29
@khalidhuseynov
Copy link
Member Author

somehow selenium tests keep error with

Tests in error: 
  ParagraphActionsIT.testRemoveButton:145->AbstractZeppelinIT.waitForParagraph:84->AbstractZeppelinIT.pollingWait:110 » Timeout
  ParagraphActionsIT.testMoveUpAndDown:182->AbstractZeppelinIT.waitForParagraph:84->AbstractZeppelinIT.pollingWait:110 » Timeout
  ParagraphActionsIT.testCreateNewButton:77->AbstractZeppelinIT.waitForParagraph:84->AbstractZeppelinIT.pollingWait:110 » Timeout

which is not related, will be reopening.
ready for review

@khalidhuseynov khalidhuseynov force-pushed the update-api/pass-auth-info-to-repo branch 7 times, most recently from e0109f7 to 0b2d122 Compare June 16, 2016 01:56
@echarles
Copy link
Member

LGTM

I have tested and works well for me.
Gone through the code and changes make sense.

Will be useful to get it into 0.6 release (especially if #836 is also in 0.6, as methods are added in the NotebookServer, which will have impact on this PR).

@Leemoonsoo
Copy link
Member

Thanks @khalidhuseynov for the improvement.
LGTM and merge it into 0.6 and master if there're no more discussions.

@khalidhuseynov khalidhuseynov force-pushed the update-api/pass-auth-info-to-repo branch from 0b2d122 to e628fa8 Compare June 17, 2016 07:37
@khalidhuseynov khalidhuseynov force-pushed the update-api/pass-auth-info-to-repo branch from e628fa8 to b91e78a Compare June 17, 2016 07:46
@khalidhuseynov
Copy link
Member Author

rebased from master

@vgmartinez
Copy link
Contributor

LGTM...I have tested and works well for me.

@asfgit asfgit closed this in 4a0dce5 Jun 18, 2016
asfgit pushed a commit that referenced this pull request Jun 18, 2016
This PR is to make available information on the currently authenticated user(subject) in the Notebook storage level. It can be used for multiple purposes (ACL, login to third parties, etc.) once storage layer is user aware. It basically updates NotebookRepo api with additional user info

Improvement

* [x] - add authInfo(subject) to list()
* [x] - add authInfo(subject) to get()
* [x] - add authInfo(subject) to save()
* [x] - add authInfo(subject) to remove()

storage layer should be working as before with and without authenticated user, green CI

* Does the licenses files need update? No
* Is there breaking changes for older versions? not breaking, but some api changes
* Does this needs documentation? No

Author: Khalid Huseynov <[email protected]>

Closes #998 from khalidhuseynov/update-api/pass-auth-info-to-repo and squashes the following commits:

b91e78a [Khalid Huseynov] propagate subject to versioning api
f3bae60 [Khalid Huseynov] fix checkstyle
bb57eae [Khalid Huseynov] address changes for job management pr after rebasing
8b48577 [Khalid Huseynov] fix test after master merge
a69d04f [Khalid Huseynov] add descriptions to NotebookRepo interface
0bf40b3 [Khalid Huseynov] propagate changes to tests
aa95537 [Khalid Huseynov] propagate changes upstream
a0ebd14 [Khalid Huseynov] add subject to checkpoint signature of all repos
50ba14a [Khalid Huseynov] add subject to NotebookRepo api
bd0a290 [Khalid Huseynov] propagate changes to tests
91426af [Khalid Huseynov] propagate changes with remove upstream
232d1af [Khalid Huseynov] propagate remove(noteId, subject) to all repo signatures
d0d7b98 [Khalid Huseynov] add subject to repo remove api
21f189d [Khalid Huseynov] propagate changes to save into tests
b5f88e2 [Khalid Huseynov] propagate subject changes upstream
b7b007a [Khalid Huseynov] add subject to all repo signatures
0a4a8d2 [Khalid Huseynov] add subject to repo save api
8fdaed3 [Khalid Huseynov] propagate changes to tests
3ea544d [Khalid Huseynov] propagate changes up to Notebook
91fc500 [Khalid Huseynov] modify all repo signatures with get(noteId, subject)
fb93e22 [Khalid Huseynov] add subject to repo api for get
7d964c7 [Khalid Huseynov] propagate list(subject) to tests
8e7d8bd [Khalid Huseynov] propagate changes to list up
f66dc1b [Khalid Huseynov] modify all repo signatureswith list(subject)
1c29bee [Khalid Huseynov] change api for repo list

(cherry picked from commit 4a0dce5)
Signed-off-by: Lee moon soo <[email protected]>
@khalidhuseynov khalidhuseynov deleted the update-api/pass-auth-info-to-repo branch June 20, 2016 07:04
Leemoonsoo added a commit to Leemoonsoo/zeppelin that referenced this pull request Jun 22, 2016
@Leemoonsoo Leemoonsoo mentioned this pull request Jun 22, 2016
1 task
asfgit pushed a commit that referenced this pull request Jun 22, 2016
### What is this PR for?
There were some mistake merging #998 into branch-0.6

### What type of PR is it?
Hot Fix

### Todos
* [x] - fix mistake

Author: Lee moon soo <[email protected]>

Closes #1065 from Leemoonsoo/branch-0.6-fix and squashes the following commits:

54cd601 [Lee moon soo] Fix merge mistake from #998
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants